PDU Type Setting Method, UE Policy Setting Method, and Related Entity

ABSTRACT

A protocol data unit (PDU) type setting method, a user equipment (UE) policy setting method, and a related entity, where the PDU type setting method includes: setting, by UE, a requested PDU type of a PDU session in a process of establishing the PDU session, where the requested PDU type of the PDU session is set by the UE based on a first condition, the first condition includes an Internet Protocol (IP) version corresponding to an application, and the application is associated with the PDU session. In the embodiments of the present disclosure, the requested PDU type of the PDU session can be consistent with a PDU type requested by the application, such that the application can normally perform communication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/787,655, filed on Feb. 11, 2020, which is a continuation ofInternational Patent Application No. PCT/CN2017/097107, filed on Aug.11, 2017. Both of the aforementioned applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

This application relates to the communications field, and in particular,to a protocol data unit (PDU) type setting method, a user equipment (UE)policy setting method, and a related entity, and the related entityincludes UE and a policy control function (PCF) entity.

BACKGROUND

An Internet Protocol (IP) address management part in the 5th generation(5G) mobile communication technology protocol specifies the followingcontent: a UE sets a requested PDU type based on an IP stack capabilityof the UE and a configuration of a data network name (DNN) in a processof establishing a PDU session. The requested PDU type is “IP” when IPversions supported by the DNN configured in the UE are the InternetProtocol version 6 (IPv6) and the Internet Protocol version 4 (IPv4).The PDU type “IP” indicates that IP versions of the PDU session are IPv4and IPv6. The requested PDU type is “IPv4” when an IP version supportedby the DNN configured in the UE is only IPv4. The PDU type “IPv4”indicates that an IP version of the PDU session is IPv4. The requestedPDU type is “IPv6” when an IP version supported by the DNN configured inthe UE is only IPv6. The PDU type “IPv6” indicates that an IP version ofthe PDU session is IPv6. When the DNN configured in the UE does notsupport a specified IP version, the UE sets the requested PDU type basedon the IP stack capability of the UE. For example, the PDU typerequested by the UE whose IP stack capabilities are IPv4 and IPv6 is“IP”. When the DNN configured in the UE does not support a specified IPversion and an IP version capability (namely, the IP stack capability)of the UE is unknown, the UE sets the requested PDU type to “IP”. The IPstack capability of the UE may also be referred to as the IP versioncapability or a device capability of the UE, the IP version supported bythe DNN may also be referred to as a DNN capability, and the requestedPDU type of the PDU session may be referred to as a requested IP versionof the PDU session. A correspondence among the IP stack capability ofthe UE, the IP version supported by the DNN, and the requested PDU typeof the PDU session may be shown in Table 1.

TABLE 1 A table of a correspondence among an IP stack capability of UE,an IP version supported by a DNN, and a requested PDU type of a PDUsession IP stack IP version Requested PDU type capability of UEsupported by a DNN of a PDU session IPv4 IPv4 IPv4 IPv6 IPv6 IPv6 IPv4IPv4 and IPv6 IPv4 IPv6 IPv4 and IPv6 IPv6 IPv4 and IPv6 IPv4 IPv4 IPv4and IPv6 IPv6 IPv6 IPv4 and IPv6 IPv4 and IPv6 IP (IPv4 and IPv6)

It can be learned from Table 1 that, when the UE requests to establishthe PDU session, the requested PDU type of the PDU session is determinedbased on the IP version supported by the DNN and the IP stack capabilityof the UE. A principle is to select an IP version jointly supported bythe IP stack capability of the UE and the IP version supported by theDNN, that is, select an intersection of the IP stack capability of theUE and the IP version supported by the DNN.

It can be learned from other approaches that, when the UE requests toestablish the PDU session, the requested PDU type of the PDU session isdetermined based on the IP version supported by the DNN and the IP stackcapability of the UE. However, if the UE requests a PDU sessionassociated with a specific application, and the application has aspecified IP version, an IP version selected based on the IP versionsupported by the DNN and the IP stack capability of the UE may beinconsistent with an IP version requested by the application. Forexample, if IP versions supported by the DNN are IPv4 and IPv6, and IPstack capabilities of the UE are IPv4 and IPv6, the PDU type requestedby the UE when the UE initiates the PDU session may be IPv4 or IPv6. Ifthe requested PDU type of the PDU session is IPv4, but a PDU typerequested by the application is IPv6, the requested PDU type of the PDUsession is inconsistent with the PDU type requested by the application.Consequently, the application cannot normally perform communication.

SUMMARY

Embodiments of the present disclosure provide a PDU type setting method,a UE policy setting method, and a related entity, such that a requestedPDU type of a PDU session can be consistent with a PDU type requested byan application, and the application can normally perform communication.

According to a first aspect, a PDU type setting method is provided. A UEsets a requested PDU type of a PDU session in a process of establishingthe PDU session, where the requested PDU type of the PDU session is setby the UE based on a first condition, where the first condition includesan IP version corresponding to an application associated with the PDUsession. It may be understood that, that the application is associatedwith the PDU session means that the application transmits data using thePDU session or transmits data traffic of the application using the PDUsession.

In this embodiment of the present disclosure, when setting the requestedPDU type of the PDU session in the process of establishing the PDUsession, the UE considers the IP version corresponding to theapplication associated with the PDU session. Therefore, the requestedPDU type of the PDU session can be consistent with a PDU type requestedby the application, such that the application can normally performcommunication.

In a possible implementation, before the UE sets the requested PDU typeof the PDU session, the UE receives a UE policy from a PCF, where the UEpolicy includes the IP version corresponding to the application. In thisimplementation, the UE receives the UE policy from the PCF, where the UEpolicy includes the IP version corresponding to the application. Assuch, the UE can set the requested PDU type of the PDU session based onthe IP version corresponding to the application.

In a possible implementation, before the UE sets the requested PDU typeof the PDU session, the UE receives a UE policy from a PCF, where the UEpolicy includes the IP version corresponding to the application and aDNN. In this implementation, the UE receives the UE policy from the PCF,where the UE policy includes the IP version corresponding to theapplication and the DNN. As such, the UE can set the requested PDU typeof the PDU session based on the IP version corresponding to theapplication and an IP version supported by the DNN.

In a possible implementation, the IP version corresponding to theapplication includes an IP version requested by the application or an IPversion recommended by the application. The IP version requested by theapplication or the IP version recommended by the application may beconfigured in the UE. The UE may obtain, from configuration information,the IP version requested by the application or the IP versionrecommended by the application. Alternatively, the UE may obtain, fromthe UE policy received from the PCF, the IP version requested by theapplication or the IP version recommended by the application. In thisimplementation, two methods that can reflect the IP version requested bythe application are provided. One form is used to directly obtain the IPversion requested by the application. The other form is used toindirectly obtain the IP version requested by the application, that is,indirectly obtain, using the IP version recommended by the application,the IP version requested by the application.

In a possible implementation, the IP version recommended by theapplication is an IP version determined based on an IP version supportedby the DNN and the IP version requested by the application. In thisimplementation, the IP version recommended by the application reflectsboth the IP version requested by the application and the IP versionsupported by the DNN, and therefore includes rich information.

In a possible implementation, the setting, by UE, a requested PDU typeof a PDU session in a process of establishing the PDU session includessetting, by the UE in the process of establishing the PDU session, therequested PDU type of the PDU session to the IP version corresponding tothe application. In this implementation, both an IP stack capability ofthe UE and the IP version supported by the DNN usually support both IPv4and IPv6. Therefore, processing resources can be saved when only the IPversion corresponding to the application is considered to set therequested PDU type of the PDU session.

In a possible implementation, the first condition further includes atleast one of the following: an IP stack capability of the UE or the IPversion supported by the DNN. In this implementation, when setting therequested PDU type of the PDU session, the UE not only considers the IPversion corresponding to the application, but also considers the IPstack capability of the UE and/or the IP version supported by the DNN,to adapt to a case in which at least one of the IP stack capability ofthe UE and the IP version supported by the DNN does not support bothIPv4 and IPv6.

In a possible implementation, when the first condition includes the IPversion corresponding to the application and the IP stack capability ofthe UE, the UE sets, in the process of establishing the PDU session, therequested PDU type of the PDU session to an intersection of the IPversion corresponding to the application and the IP stack capability ofthe UE. In this implementation, the UE sets the requested PDU type ofthe PDU session to the intersection of the IP version corresponding tothe application and the IP stack capability of the UE. As such, the PDUtype meets both an application requirement and a UE capabilityrequirement, thereby correspondingly improving a possibility that theapplication can normally perform communication.

In a possible implementation, when the IP version corresponding to theapplication is the IP version requested by the application, and thefirst condition includes the IP version requested by the application andthe IP version supported by the DNN, the UE sets, in the process ofestablishing the PDU session, the requested PDU type of the PDU sessionto an intersection of the IP version requested by the application andthe IP version supported by the DNN. In this implementation, the UE setsthe requested PDU type of the PDU session to the intersection of the IPversion requested by the application and the IP version supported by theDNN. As such, the PDU type meets both an application requirement and aDNN capability requirement, thereby correspondingly improving apossibility that the application can normally perform communication.

In a possible implementation, when the IP version corresponding to theapplication is the IP version requested by the application, and thefirst condition includes the IP version requested by the application,the IP stack capability of the UE, and the IP version supported by theDNN, the UE sets, in the process of establishing the PDU session, therequested PDU type of the PDU session to an intersection of the IPversion requested by the application, the IP stack capability of the UE,and the IP version supported by the DNN. In this implementation, the UEsets the requested PDU type of the PDU session to the intersection ofthe IP version requested by the application, the IP stack capability ofthe UE, and the IP version supported by the DNN, such that the PDU typemeets an application requirement, a UE capability requirement, and a DNNcapability requirement, thereby correspondingly improving a possibilitythat the application can normally perform communication.

According to a second aspect, a UE policy setting method is provided. APCF sends a UE policy to UE, where the UE policy includes an IP versioncorresponding to an application. The IP version corresponding to theapplication is used by the UE to set a requested PDU type of a PDUsession, and the application is associated with the PDU session.

In this embodiment of the present disclosure, the PCF sends the UEpolicy to the UE, where the UE policy includes the IP versioncorresponding to the application. As such, the UE can set the requestedPDU type of the PDU session based on the IP version corresponding to theapplication.

In a possible implementation, the IP version corresponding to theapplication includes an IP version requested by the application or an IPversion recommended by the application. In this implementation, the IPversion corresponding to the application can have different forms, andtherefore is highly flexible.

In a possible implementation, before the PCF sends the UE policy to theUE, the PCF determines, based on an IP version supported by a DNN andthe IP version requested by the application, the IP version recommendedby the application, where the IP version corresponding to theapplication is the IP version recommended by the application. In thisimplementation, the IP version recommended by the application reflectsboth the IP version requested by the application and the IP versionsupported by the DNN, and therefore includes a large amount ofinformation.

In a possible implementation, the UE policy further includes the DNN. Inthis implementation, the PCF sends the UE policy to the UE, such thatthe UE can not only obtain the IP version corresponding to theapplication, but also obtain the DNN. In this way, when setting therequested PDU type of the PDU session, the UE can not only consider theIP version corresponding to the application associated with the PDUsession, but also consider the IP version supported by the DNN.Therefore, the requested PDU type of the PDU session can be consistentwith a PDU type requested by the application, and can also be consistentwith the IP version supported by the DNN.

According to a third aspect, UE is provided. The UE may implement afunction performed in the method design according to the first aspect,and the function may be implemented by hardware, or may be implementedby hardware by executing corresponding software. The hardware or thesoftware includes one or more modules corresponding to the function.

According to a fourth aspect, UE is provided. A structure of the UEincludes a processor and a memory. The processor is configured tosupport the UE in performing a corresponding function in the methodaccording to the first aspect. The memory is configured to be coupled tothe processor, and the memory stores a program instruction and data thatare necessary for the UE. The UE may further include a communicationsinterface configured to send or receive information or the like.

According to a fifth aspect, a PCF is provided. The PCF may implement afunction performed in the method design according to the second aspect.Additionally, the function may be implemented by hardware, or may beimplemented by hardware by executing corresponding software. Thehardware or the software includes one or more modules corresponding tothe function.

According to a sixth aspect, a PCF is provided. A structure of the PCFincludes a processor and a memory. The processor is configured tosupport the PCF in performing a corresponding function in the methodaccording to the second aspect. The memory is configured to be coupledto the processor, and the memory stores a program instruction and datathat are necessary for the PCF. The PCF may further include acommunications interface configured to send or receive information orthe like.

According to a seventh aspect, a chip is provided. The chip may bedisposed in a device, and the chip includes a processor and aninterface. The processor is configured to support the chip in performinga corresponding function in the method according to the first aspect.The interface is configured to support the chip in communicating withanother chip or another network element. The chip may further include amemory. The memory is configured to be coupled to the processor, and thememory stores a program instruction and data that are necessary for thechip.

According to an eighth aspect, a chip is provided. The chip may bedisposed in a device, and the chip includes a processor and aninterface. The processor is configured to support the chip in performinga corresponding function in the method according to the second aspect.The interface is configured to support the chip in communicating withanother chip or another network element. The chip may further include amemory. The memory is configured to be coupled to the processor, and thememory stores a program instruction and data that are necessary for thechip.

According to a ninth aspect, a computer storage medium is provided. Thecomputer storage medium is configured to store a computer softwareinstruction used by the foregoing UE, where the computer storage mediumincludes a program designed to perform the first aspect.

According to a tenth aspect, a computer storage medium is provided. Thecomputer storage medium is configured to store a computer softwareinstruction used by the foregoing PCF, where the computer storage mediumincludes a program designed to perform the second aspect.

According to an eleventh aspect, a computer program product is provided,including an instruction. When the program is executed by a computer,the instruction enables the computer to perform a function performed bythe UE in the method design according to the first aspect.

According to a twelfth aspect, an embodiment of the present disclosureprovides a computer program product, including an instruction. When theprogram is executed by a computer, the instruction enables the computerto perform a function performed by the PCF in the method designaccording to the second aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of an application scenario according to anembodiment of the present disclosure;

FIG. 2 is a schematic communication diagram of a PDU type setting methodaccording to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a method in which a requested IP version of aPDU session is determined based on an IP version requested by anapplication according to an embodiment of the present disclosure;

FIG. 4 is a schematic communication diagram of another PDU type settingmethod according to an embodiment of the present disclosure;

FIG. 5 is a flowchart of a method in which a requested PDU type of a PDUsession is determined based on an IP version recommended by anapplication according to an embodiment of the present disclosure;

FIG. 6 is a schematic communication diagram of a method for obtaining aURSP according to an embodiment of the present disclosure;

FIG. 7 is a structural diagram of UE according to an embodiment of thepresent disclosure;

FIG. 8 is a structural diagram of another UE according to an embodimentof the present disclosure;

FIG. 9 is a structural diagram of a PCF according to an embodiment ofthe present disclosure; and

FIG. 10 is a structural diagram of another PCF according to anembodiment of the present disclosure.

DESCRIPTION OF EMBODIMENTS

Embodiments of the present disclosure provide a PDU type setting methodin which a UE sets a requested PDU type of a PDU session in a process ofestablishing the PDU session. The requested PDU type of the PDU sessionis set by the UE based on a first condition, where the first conditionincludes an IP version corresponding to an application associated withthe PDU session. It may be understood that, that the application isassociated with the PDU session means that the application transmitsdata using the PDU session or transmits data traffic of the applicationusing the PDU session.

In the embodiments of the present disclosure, when setting the requestedPDU type of the PDU session in the process of establishing the PDUsession, the UE considers the IP version corresponding to theapplication associated with the PDU session. Therefore, the requestedPDU type of the PDU session can be consistent with a PDU type requestedby the application, such that the application can normally performcommunication.

In a possible implementation, the IP version corresponding to theapplication includes an IP version requested by the application or an IPversion recommended by the application. The IP version requested by theapplication or the IP version recommended by the application may beconfigured in the UE. The UE may obtain, from configuration information,the IP version requested by the application or the IP versionrecommended by the application. Alternatively, the UE may obtain, from aUE policy received from a PCF, the IP version requested by theapplication or the IP version recommended by the application. In thisimplementation, two methods that can reflect the IP version requested bythe application are provided. One form is used to directly obtain the IPversion requested by the application. The other form is used toindirectly obtain the IP version requested by the application, that is,indirectly obtain, using the IP version recommended by the application,the IP version requested by the application.

FIG. 1 is a schematic diagram of an application scenario according to anembodiment of the present disclosure. The scenario is based on a 5Gsystem architecture. Main network entities in the scenario include: a UE101 configured to: store one or more applications; and establish a PDUsession, such that the application can normally perform communication,where the UE 101 needs to set a requested PDU type of the PDU session ina process of establishing the PDU session; a mobility managementfunction such as an Access and Mobility Management Function (AMF) entity102 configured to be responsible for mobility management of the UE 101,including registration, location update, and the like; a PCF 103configured to store a UE policy, including a user equipment routeselection policy (URSP); and a unified data management (UDM) functionentity 104 configured to store subscription information of the UE 101,including an international mobile subscriber identity (IMSI) of the UE101 and a context of the UE 101.

The UE policy may be but is not limited to the URSP. It can be learnedfrom descriptions of the URSP in the 5G protocol that the PCF stores theURSP, and a DNN selection policy in the URSP is used to select one ormore DNNs for the PDU session. The URSP may include one or more rulescorresponding to each application. The rule may be formulated by anoperator or formulated by an operator based on a requirement of anapplication service provider. The rule usually includes a DNN. Table 2shows an example of a common URSP. Table 2 also shows a correspondencebetween an application name and a DNN.

TABLE 2 A table of a correspondence between an application name and aDNN in a URSP Application name DNN App 1 Default App 2 Internet

It can be learned from Table 2 that, because the DNN corresponding tothe App 1 is not specified in the URSP, the UE may consider the DNN ofthe application as a default value, where the DNN corresponding to theApp 2 is the Internet. After determining the DNN corresponding to theapplication, the UE may determine the requested PDU type of the PDUsession based on an IP version supported by the DNN, where the requestedPDU type of the PDU session is a requested IP version of the PDUsession. Alternatively, the UE may determine the requested PDU type ofthe PDU session based on an IP version supported by the DNN and an IPstack capability of the UE.

It can be learned from the foregoing analysis that the common URSPincludes only the DNN, and does not include a PDU type requested by theapplication (namely, an IP version requested by the application). Whendetermining the requested PDU type of the PDU session, the UE usuallydetermines the requested PDU type of the PDU session based on the IPversion supported by the DNN and/or the IP stack capability of the UE.As a result, the requested PDU type of the PDU session may beinconsistent with the IP version requested by the application, andconsequently the application cannot normally perform communication.

In an embodiment of the present disclosure, the URSP is modified suchthat the UE can obtain an IP version requested by an application. Table3 shows an example of a modified URSP provided in this embodiment of thepresent disclosure. Table 3 also shows a correspondence between anapplication name and an IP version requested by an application.

TABLE 3 A table of a correspondence between an application name and anIP version requested by an application in a URSP Application name IPversion requested by an application App 1 IPv4 App 2 IPv6

It can be learned from Table 3 that the IP version requested by the App1 is IPv4 and the IP version requested by the App 2 is IPv6. Afterdetermining the application associated with the PDU session, the UE maydetermine a requested IP version of the PDU session based on the IPversion requested by the application, that is, determine the requestedPDU type of the PDU session. Alternatively, the UE may determine arequested IP version of the PDU session based on the IP versionrequested by the application and an IP stack capability of the UE.

In another embodiment of the present disclosure, the URSP is modified,such that the UE can obtain an IP version requested by an application.Table 4 shows an example of a modified URSP provided in this embodimentof the present disclosure. Table 4 also shows a correspondence among anapplication name, an IP version requested by an application, and a DNN.

TABLE 4 A table of a correspondence among an application name, an IPversion requested by an application, and a DNN in a URSP Application IPversion requested name by an application DNN App 1 IPv4 Default App 2IPv6 Internet

It can be learned from Table 4 that the IP version requested by the App1 is IPv4, the DNN of the App 1 is considered as a default value, the IPversion requested by the App 2 is IPv6, and the DNN corresponding to theApp 2 is the Internet. After determining the application associated withthe PDU session, the UE may determine a requested IP version of the PDUsession based on the IP version requested by the application and an IPversion supported by the DNN. Alternatively, the UE may determine arequested IP version of the PDU session based on the IP versionrequested by the application, an IP version supported by the DNN, and anIP stack capability of the UE.

In still another embodiment of the present disclosure, the URSP ismodified, such that the UE can obtain an IP version recommended by anapplication. Table 5 shows an example of a modified URSP provided inthis embodiment of the present disclosure. Table 5 also shows acorrespondence between an application name and an IP version recommendedby an application.

TABLE 5 A table of a correspondence between an application name and anIP version recommended by an application in a URSP Application name IPversion recommended by an application App 1 IPv4 App 2 IPv6

It can be learned from Table 5 that the IP version recommended by theApp 1 is IPv4 and the IP version recommended by the App 2 is IPv6. Afterdetermining the application associated with the PDU session, the UE maydetermine a requested IP version of the PDU session based on the IPversion recommended by the application. Alternatively, the UE maydetermine a requested IP version of the PDU session based on the IPversion recommended by the application and an IP stack capability of theUE.

An embodiment of the present disclosure provides a PDU type settingmethod. The method may be based on the application scenario shown inFIG. 1. A UE sets a requested PDU type of a PDU session in a process ofestablishing the PDU session. The requested PDU type of the PDU sessionis set by the UE based on a first condition. The first conditionincludes an IP version corresponding to an application, where theapplication is associated with the PDU session. It may be understoodthat the UE may obtain the IP version corresponding to the applicationfrom a URSP received from a PCF, and this is not limited. The IP versioncorresponding to the application includes an IP version requested by theapplication or an IP version recommended by the application. The IPversion recommended by the application is an IP version determined basedon an IP version supported by a DNN and the IP version requested by theapplication.

In this embodiment of the present disclosure, when setting the requestedPDU type of the PDU session in the process of establishing the PDUsession, the UE considers the IP version corresponding to theapplication associated with the PDU session. Therefore, the requestedPDU type of the PDU session can be consistent with a PDU type requestedby the application, such that the application can normally performcommunication.

The following describes, using an example in which the PCF sends one ofthe foregoing modified URSPs to the UE, the PDU type setting methodprovided in this embodiment of the present disclosure.

FIG. 2 is a schematic communication diagram of a PDU type setting methodaccording to an embodiment of the present disclosure. An IP versioncorresponding to an application is an IP version requested by theapplication. The method includes the following steps.

Step 201. A PCF sends a UE policy to a UE, where the UE policy includesan IP version requested by an application and a DNN.

Applications may have different DNNs. In this case, the DNN is a DNN ofthe application. For example, if the DNN is the Internet, it indicatesthat a data network of the application is the Internet.

In an example, the IP version requested by the application may include“IPv4”, “IPv6”, and “IP”. “IP” indicates that the application supportsboth IPv4 and IPv6.

Step 202. The UE sets, based on the IP version requested by theapplication, an IP version supported by the DNN, and an IP stackcapability of the UE, a requested PDU type of a PDU session in a processof establishing the PDU session, where the application is associatedwith the PDU session.

It may be understood that, that the application is associated with thePDU session means that the application transmits data using the PDUsession or transmits data traffic of the application using the PDUsession.

The UE may determine, based on the DNN included in the UE policy, the IPversion supported by the DNN. A correspondence between a DNN and an IPversion supported by the DNN may be pre-stored in the UE, and the IPstack capability of the UE may also be pre-stored in the UE.

In an example, the UE sets, in the process of establishing the PDUsession, the requested PDU type of the PDU session to an intersection ofthe IP version requested by the application, the IP stack capability ofthe UE, and the IP version supported by the DNN. To be more specific,the UE selects, as the requested PDU type of the PDU session, an IPversion jointly supported by the IP version requested by theapplication, the IP stack capability of the UE, and the IP versionsupported by the DNN. For example, if the IP version requested by theapplication is IPv4, and both the IP stack capability of the UE and theIP version supported by the DNN support both IPv4 and IPv6, the IPversion jointly supported by the IP version requested by theapplication, the IP stack capability of the UE, and the IP versionsupported by the DNN is IPv4. In this case, IPv4 is used as therequested PDU type of the PDU session.

In this implementation, the UE sets the requested PDU type of the PDUsession to the intersection of the IP version requested by theapplication, the IP stack capability of the UE, and the IP versionsupported by the DNN. As such, the PDU type meets an applicationrequirement, a UE capability requirement, and a DNN capabilityrequirement, thereby correspondingly improving a possibility that theapplication can normally perform communication.

The following describes, using an example, the PDU type setting methodprovided in this embodiment of the present disclosure.

FIG. 3 is a flowchart of a method in which a requested IP version of aPDU session is determined based on an IP version requested by anapplication according to an embodiment of the present disclosure. Themethod includes the following steps.

Step 301. A UE determines, based on an IP version requested by anapplication, an IP version supported by a DNN, and an IP stackcapability of the UE, a requested PDU type of a PDU session to beinitiated by the UE.

In an example, when there is an IP version jointly supported by the IPversion requested by the application, the IP version supported by theDNN, and the IP stack capability of the UE, the UE determines thejointly supported IP version as the requested PDU type of the PDUsession to be initiated by the UE, and the UE subsequently initiates thePDU session of the application based on the determined PDU type. Whenthere is no IP version jointly supported by the IP version requested bythe application, the IP version supported by the DNN, and the IP stackcapability of the UE, the UE cannot initiate the PDU session of theapplication.

Step 302. Obtain the following information: the IP version requested bythe application is IPv6, IP versions supported by the DNN are IPv4 andIPv6, and IP stack capabilities of the UE are IPv4 and IPv6.

In an example, the UE may be configured to: receive a URSP from a PCF;obtain, from the URSP, the IP version requested by the application andthe DNN; determine, based on a pre-stored correspondence between a DNNand an IP version supported by the DNN, the IP version supported by theDNN; and obtain the pre-stored IP stack capability of the UE.

Step 303. Determine, based on the information obtained in step 302, thatthe PDU type is IPv6.

In an example, the UE may select, as the requested PDU type of the PDUsession, an intersection of the IP version requested by the application,the IP version supported by the DNN, and the IP stack capability of theUE.

After determining the PDU type, the UE may subsequently perform step308.

Step 304. Obtain the following information: IP versions requested by theapplication are IPv4 and IPv6, the IP version supported by the DNN isIPv4, and IP stack capabilities of the UE are IPv4 and IPv6.

In an example, the UE may be configured to: receive a URSP from a PCF;obtain, from the URSP, the IP version requested by the application andthe DNN; determine, based on a pre-stored correspondence between a DNNand an IP version supported by the DNN, the IP version supported by theDNN; and obtain the pre-stored IP stack capability of the UE.

Step 305. Determine, based on the information obtained in step 304, thatthe PDU type is IPv4.

In an example, the UE may select, as the requested PDU type of the PDUsession, an intersection of the IP version requested by the application,the IP version supported by the DNN, and the IP stack capability of theUE.

After determining the PDU type, the UE may subsequently perform step308.

Step 306. Determine that the IP version requested by the application isIPv6, the IP version supported by the DNN is not configured, and the IPstack capability of the UE is IPv4.

In an example, the UE may be configured to: receive a URSP from a PCF;obtain, from the URSP, the IP version requested by the application andthe DNN; determine, based on a pre-stored correspondence between a DNNand an IP version supported by the DNN, the IP version supported by theDNN; and obtain the pre-stored IP stack capability of the UE.

Step 307. Determine, based on the information obtained in step 306, thatthe PDU session of the application cannot be initiated.

In an example, the UE may determine whether the IP version requested bythe application, the IP version supported by the DNN, and the IP stackcapability of the UE have an intersection. When the IP version requestedby the application, the IP version supported by the DNN, and the IPstack capability of the UE have no intersection, the UE determines thatthe PDU session of the application cannot be initiated.

Step 308. The UE initiates the PDU session of the application based onthe determined PDU type.

In an example, the UE may determine whether the IP version requested bythe application, the IP version supported by the DNN, and the IP stackcapability of the UE have an intersection. When the IP version requestedby the application, the IP version supported by the DNN, and the IPstack capability of the UE have an intersection, the UE uses, as therequested PDU type of the PDU session, the intersection of the IPversion requested by the application, the IP version supported by theDNN, and the IP stack capability of the UE. Then the UE initiates thePDU session of the application based on the determined PDU type.

It can be learned from FIG. 3 that the UE determines, based on the IPversion requested by the application, the IP version supported by theDNN, and the IP stack capability of the UE, the PDU type of the PDUsession to be initiated by the UE. If the IP version requested by theapplication, the IP version supported by the DNN, and the IP stackcapability of the UE have an intersection, the UE initiates the PDUsession of the application. If the IP version requested by theapplication, the IP version supported by the DNN, and the IP stackcapability of the UE have no intersection, the UE cannot initiate thePDU session of the application.

In this embodiment of the present disclosure, the UE first determineswhether the IP version requested by the application, the IP versionsupported by the DNN, and the IP stack capability of the UE have anintersection. When the IP version requested by the application, the IPversion supported by the DNN, and the IP stack capability of the UE haveno intersection, the UE determines that the PDU session of theapplication cannot be initiated. As such, network resources can besaved, that is, the PDU session is established without wasting thenetwork resources. When the IP version requested by the application, theIP version supported by the DNN, and the IP stack capability of the UEhave an intersection, the UE uses, as the requested PDU type of the PDUsession, the intersection of the IP version requested by theapplication, the IP version supported by the DNN, and the IP stackcapability of the UE. The UE then initiates the PDU session of theapplication based on the determined PDU type, such that a possibilitythat the application can normally perform communication can be improved.

In this embodiment of the present disclosure, because a UE policyincludes both the DNN and the IP version requested by the application,the UE may set the requested PDU type of the PDU session based on the IPversion requested by the application, the IP version supported by theDNN, and the IP stack capability of the UE. Therefore, the requested PDUtype of the PDU session can be consistent with the IP version requestedby the application, such that the application can normally performcommunication.

In addition, this embodiment of the present disclosure further providesa plurality of optional implementations.

In a possible implementation, before the UE sets the requested PDU typeof the PDU session, the UE receives the UE policy from the PCF, wherethe UE policy includes the IP version requested by the application. Thisway, the UE can set the requested PDU type of the PDU session based onthe IP version requested by the application. For example, the UE setsthe requested PDU type of the PDU session to the IP version requested bythe application. In this implementation, both the IP stack capability ofthe UE and the IP version supported by the DNN usually support both IPv4and IPv6. Therefore, processing resources can be saved when only the IPversion requested by the application is considered to set the requestedPDU type of the PDU session.

In a possible implementation, before the UE sets the requested PDU typeof the PDU session, the UE receives the UE policy from the PCF, wherethe UE policy includes the IP version requested by the application andthe DNN. As such, the UE can set the requested PDU type of the PDUsession based on the IP version requested by the application and the IPversion supported by the DNN.

For example, the UE sets, in a process of establishing the PDU session,the requested PDU type of the PDU session to an intersection of the IPversion requested by the application and the IP stack capability of theUE. In this implementation, the UE sets the requested PDU type of thePDU session to the intersection of the IP version corresponding to theapplication and the IP stack capability of the UE. As such, the PDU typemeets both an application requirement and a UE capability requirement,thereby correspondingly improving a possibility that the application cannormally perform communication.

For another example, the UE sets, in a process of establishing the PDUsession, the requested PDU type of the PDU session to an intersection ofthe IP version requested by the application and the IP version supportedby the DNN. In this implementation, the UE sets the requested PDU typeof the PDU session to the intersection of the IP version requested bythe application and the IP version supported by the DNN. As such, thePDU type meets both an application requirement and a DNN capabilityrequirement, thereby correspondingly improving a possibility that theapplication can normally perform communication.

For another example, the UE sets, in a process of establishing the PDUsession, the requested PDU type of the PDU session to the intersectionof the IP version requested by the application, the IP stack capabilityof the UE, and the IP version supported by the DNN. In thisimplementation, the UE sets the requested PDU type of the PDU session tothe intersection of the IP version requested by the application, the IPstack capability of the UE, and the IP version supported by the DNN. Assuch, the PDU type meets an application requirement, a UE capabilityrequirement, and a DNN capability requirement, thereby correspondinglyimproving a possibility that the application can normally performcommunication.

FIG. 4 is a schematic communication diagram of another PDU type settingmethod according to an embodiment of the present disclosure. An IPversion corresponding to an application is an IP version recommended bythe application. The method includes the following steps.

Step 401. A PCF sends a UE policy to UE, where the UE policy includes anIP version recommended by an application.

In an example, the PCF may determine, based on an IP version requestedby the application and an IP version supported by a DNN, the IP versionrecommended by the application. For example, an intersection of the IPversion requested by the application and the IP version supported by theDNN is used as the IP version recommended by the application.

Applications may have different DNNs. In this case, the DNN is a DNN ofthe application. For example, if the DNN is the Internet, it indicatesthat a data network of the application is the Internet.

In an example, the IP version requested by the application may include“IPv4”, “IPv6”, and “IP”. “IP” indicates that the application supportsboth IPv4 and IPv6.

Step 402. The UE sets, based on the IP version recommended by theapplication and an IP stack capability of the UE, a requested PDU typeof a PDU session in a process of establishing the PDU session, where theapplication is associated with the PDU session.

The IP stack capability of the UE may be pre-stored in the UE.

In a possible implementation, the UE sets, in the process ofestablishing the PDU session, the requested PDU type of the PDU sessionto an intersection of the IP version recommended by the application andthe IP stack capability of the UE. To be more specific, the UE selects,as the requested PDU type of the PDU session, an IP version jointlysupported by the IP version recommended by the application and the IPstack capability of the UE. For example, if the IP version recommendedby the application is IPv4, and the IP stack capability of the UEsupports both IPv4 and IPv6, the IP version jointly supported by the IPversion recommended by the application and the IP stack capability ofthe UE is IPv4. In this case, IPv4 is used as the requested PDU type ofthe PDU session.

In this implementation, the UE sets the requested PDU type of the PDUsession to the intersection of the IP version recommended by theapplication and the IP stack capability of the UE. Because the IPversion recommended by the application reflects both an applicationrequirement and a DNN capability requirement, the PDU type meets theapplication requirement, a UE capability requirement, and the DNNcapability requirement, thereby correspondingly improving a possibilitythat the application can normally perform communication.

The following describes, using an example, the PDU type setting methodprovided in this embodiment of the present disclosure.

FIG. 5 is a flowchart of a method in which a requested PDU type of a PDUsession is determined based on an IP version recommended by anapplication according to an embodiment of the present disclosure. Themethod includes the following steps.

Step 501. A UE determines, based on an IP version recommended by anapplication and an IP stack capability of the UE, a requested PDU typeof a PDU session to be initiated by the UE.

In an example, when there is an IP version jointly supported by the IPversion recommended by the application and the IP stack capability ofthe UE, the UE determines the jointly supported IP version as therequested PDU type of the PDU session to be initiated by the UE. The UEsubsequently initiates the PDU session of the application based on thedetermined PDU type. When there is no IP version jointly supported bythe IP version recommended by the application and the IP stackcapability of the UE, the UE cannot initiate the PDU session of theapplication.

Step 502. Obtain the following information: the IP version recommendedby the application is IPv6, and IP stack capabilities of the UE are IPv4and IPv6.

In an example, the UE may be configured to: receive a URSP from a PCF;obtain, from the URSP, the IP version recommended by the application;and obtain the pre-stored IP stack capability of the UE.

Step 503. Determine, based on the information obtained in step 502, thatthe PDU type is IPv6.

In an example, the UE may select, as the requested PDU type of the PDUsession, an intersection of the IP version recommended by theapplication and the IP stack capability of the UE.

After determining the PDU type, the UE may subsequently perform step506.

Step 504. Obtain the following information: the IP version recommendedby the application is IPv6, and the IP stack capability of the UE isIPv4.

In an example, the UE may be configured to: receive a URSP from a PCF;obtain, from the URSP, the IP version recommended by the application;and obtain the pre-stored IP stack capability of the UE.

Step 505. Determine, based on the information obtained in step 504, thatthe PDU session of the application cannot be initiated.

In an example, the UE may determine whether the IP version recommendedby the application and the IP stack capability of the UE have anintersection. When the IP version recommended by the application and theIP stack capability of the UE have no intersection, the UE determinesthat the PDU session of the application cannot be initiated.

Step 506. The UE initiates the PDU session of the application based onthe determined PDU type.

In an example, the UE may determine whether the IP version recommendedby the application and the IP stack capability of the UE have anintersection. When the IP version recommended by the application and theIP stack capability of the UE have an intersection, the UE uses, as therequested PDU type of the PDU session, the intersection of the IPversion recommended by the application and the IP stack capability ofthe UE. The then UE initiates the PDU session of the application basedon the determined PDU type.

It can be learned from FIG. 5 that the UE determines, based on the IPversion recommended by the application and the IP stack capability ofthe UE, the PDU type of the PDU session to be initiated by the UE. Ifthe IP version recommended by the application and the IP stackcapability of the UE have an intersection, the UE initiates the PDUsession of the application. If the IP version recommended by theapplication and the IP stack capability of the UE have no intersection,the UE cannot initiate the PDU session of the application.

In this embodiment of the present disclosure, the UE first determineswhether the IP version recommended by the application and the IP stackcapability of the UE have an intersection. When the IP versionrecommended by the application and the IP stack capability of the UEhave no intersection, the UE determines that the PDU session of theapplication cannot be initiated. As such, network resources can besaved, that is, the PDU session is established without wasting thenetwork resources. When the IP version recommended by the applicationand the IP stack capability of the UE have an intersection, the UE uses,as the requested PDU type of the PDU session, the intersection of the IPversion recommended by the application and the IP stack capability ofthe UE. Then the UE initiates the PDU session of the application basedon the determined PDU type, such that a possibility that the applicationcan normally perform communication can be improved.

In this embodiment of the present disclosure, because a UE policyincludes the IP version recommended by the application, and the IPversion recommended by the application is determined based on an IPversion requested by the application and an IP version supported by aDNN, the UE may set the requested PDU type of the PDU session based onthe IP version recommended by the application and the IP stackcapability of the UE. Therefore, the requested PDU type of the PDUsession can be consistent with the IP version requested by theapplication, such that the application can normally performcommunication.

In addition, this embodiment of the present disclosure further providesa plurality of optional implementations.

In a possible implementation, before the UE sets the requested PDU typeof the PDU session, the UE receives the UE policy from the PCF. The UEpolicy includes the IP version recommended by the application, such thatthe UE can set the requested PDU type of the PDU session based on the IPversion recommended by the application. The IP version recommended bythe application is an IP version determined based on the IP versionsupported by the DNN and the IP version requested by the application. Tobe more specific, an intersection of the IP version supported by the DNNand the IP version requested by the application may be used as the IPversion recommended by the application. For example, if IP versionssupported by the DNN are IPv4 and IPv6, and the IP version requested bythe application is IPv4, the IP version recommended by the applicationis IPv4.

For example, the UE sets, in a process of establishing the PDU session,the requested PDU type of the PDU session to the IP version recommendedby the application. In this implementation, the IP stack capability ofthe UE usually supports both IPv4 and IPv6. Therefore, processingresources can be saved when only the IP version recommended by theapplication is considered to set the requested PDU type of the PDUsession.

For another example, the UE sets, in a process of establishing the PDUsession, the requested PDU type of the PDU session to the intersectionof the IP version recommended by the application and the IP stackcapability of the UE. In this implementation, the UE sets the requestedPDU type of the PDU session to the intersection of the IP versionrecommended by the application and the IP stack capability of the UE. Assuch, the PDU type meets an application requirement, a DNN capabilityrequirement, and a UE capability requirement, thereby correspondinglyimproving a possibility that the application can normally performcommunication.

The following describes, using an embodiment, a process in which the UEobtains the URSP.

FIG. 6 is a schematic communication diagram of a method for obtaining aURSP according to an embodiment of the present disclosure. The URSPincludes an IP version requested by an application or an IP versionrecommended by an application. The method includes the following steps.

Step 601. A UE sends a registration request message to an AMF, where theregistration request message carries a globally unique temporaryidentity (GUTI) of the UE.

Step 602. The AMF sends an update location request message to a unifieddata management (UDM) function entity, where the update location requestmessage carries the GUTI of the UE.

Step 603. The UDM sends an update location response (e.g., UpdateLocation Acknowledgment (Ack)) message to the AMF, where the updatelocation response message carries subscription information of the userequipment (UE's Subscription). The subscription information of the userequipment includes an international mobile subscriber identity (IMSI) ofthe UE.

In addition to the IMSI of the UE, the subscription information of theuser equipment may include other subscription information. Details arenot described herein.

Step 604. The AMF sends a context establishment request message of theUE to a PCF, where the context establishment request message carries theIMSI of the UE.

Step 605. The PCF sends a context establishment response message of theUE to the AMF, where the context establishment response message carriesthe IMSI of the UE and a URSP.

The URSP includes an IP version requested by an application or an IPversion recommended by an application.

In an example, the URSP includes the IP version recommended by theapplication.

Before the PCF sends the URSP to the UE, the PCF determines, based on anIP version supported by a DNN and the IP version requested by theapplication, the IP version recommended by the application. In thisimplementation, the IP version recommended by the application reflectsboth the IP version requested by the application and the IP versionsupported by the DNN, and therefore includes a large amount ofinformation.

In another example, the URSP includes the IP version requested by theapplication and a DNN. In this implementation, the PCF sends the URSP tothe UE, such that the UE can not only obtain the IP version requested bythe application, but also obtain the DNN. This way, when setting arequested PDU type of a PDU session, the UE can not only consider the IPversion requested by the application associated with the PDU session,but also consider an IP version supported by the DNN. Therefore, therequested PDU type of the PDU session can be consistent with a PDU typerequested by the application, and can also be consistent with the IPversion supported by the DNN.

Step 606. The AMF sends a registration response (e.g., RegistrationAccept) message to the UE, where the registration response messagecarries the URSP.

The URSP includes the IP version requested by the application or the IPversion recommended by the application.

Optionally, this embodiment of the present disclosure further includesthe following step.

Step 607. The UE sets, based on an IP version requested by anapplication or an IP version recommended by an application, a requestedPDU type of a PDU session in a process of establishing the PDU session,where the application is associated with the PDU session.

In this embodiment of the present disclosure, the PCF sends the URSP tothe UE, where the URSP includes the IP version requested by theapplication or the IP version recommended by the application. As such,the UE can set the requested PDU type of the PDU session based on the IPversion requested by the application or the IP version recommended bythe application, thereby correspondingly improving a possibility thatthe application normally performs communication.

The foregoing mainly describes the solutions in the embodiments of thepresent disclosure from the perspective of interaction between networkelements. It may be understood that, to implement the foregoingfunctions, the network elements such as the UE and the PCF include acorresponding hardware structure and/or software module for performingthe functions. A person of ordinary skill in the art should be awarethat, units and algorithm steps in the examples described with referenceto the embodiments disclosed in this specification may be implemented byhardware or a combination of hardware and computer software in thepresent disclosure. Whether a function is performed by hardware orhardware driven by computer software depends on particular applicationsand design constraints of the technical solutions. A person skilled inthe art may use different methods to implement the described functionsfor each particular application, but it should not be considered thatthe implementation goes beyond the scope of the present disclosure.

In the embodiments of the present disclosure, the UE, the PCF, and thelike may be divided into function modules based on the foregoing methodexamples. For example, each function module may be obtained throughdivision for each corresponding function, or two or more functions maybe integrated into one processing module. The integrated module may beimplemented in a form of hardware, or may be implemented in a form of asoftware function module. It should be noted that the module division inthe embodiments of the present disclosure is an example, and is merelylogical function division. There may be another division manner inactual implementation.

When an integrated module is used, FIG. 7 is a possible schematicstructural diagram of the UE in the foregoing embodiment. The UE 700includes a processing module 702 and a communications module 703. Theprocessing module 702 is configured to control and manage an action ofthe UE.

In an example, the processing module 702 is configured to set arequested PDU type of a PDU session in a process of establishing the PDUsession using the communications module 703. The requested PDU type ofthe PDU session is set based on a first condition, which includes an IPversion corresponding to an application, where the application isassociated with the PDU session.

In an example, before the processing module 702 sets the requested PDUtype of the PDU session, the processing module 702 is further configuredto receive a UE policy from a PCF using the communications module 703.The UE policy includes the IP version corresponding to the application.

In an example, before the processing module 702 sets the requested PDUtype of the PDU session, the processing module 702 is further configuredto receive a UE policy from a PCF using the communications module 703.The UE policy includes the IP version corresponding to the applicationand a DNN.

In an example, the IP version corresponding to the application includesan IP version requested by the application or an IP version recommendedby the application.

In an example, the IP version recommended by the application is an IPversion determined based on an IP version supported by the DNN and theIP version requested by the application.

An example in which the processing module 702 sets a requested PDU typeof a PDU session in a process of establishing the PDU session using thecommunications module 703 includes: setting, in the process ofestablishing the PDU session using the communications module 703, therequested PDU type of the PDU session to the IP version corresponding tothe application.

In an example, the first condition further includes at least one of thefollowing: an IP stack capability of the UE or the IP version supportedby the DNN.

An example in which the processing module 702 sets a requested PDU typeof a PDU session in a process of establishing the PDU session using thecommunications module 703 includes: when the first condition includesthe IP version corresponding to the application and the IP stackcapability of the UE, setting, in the process of establishing the PDUsession, the requested PDU type of the PDU session to an intersection ofthe IP version corresponding to the application and the IP stackcapability of the UE.

An example in which the processing module 702 sets a requested PDU typeof a PDU session in a process of establishing the PDU session using thecommunications module 703 includes: when the IP version corresponding tothe application is the IP version requested by the application, and thefirst condition includes the IP version requested by the application andthe IP version supported by the DNN, setting, in the process ofestablishing the PDU session, the requested PDU type of the PDU sessionto an intersection of the IP version requested by the application andthe IP version supported by the DNN.

An example in which the processing module 702 sets a requested PDU typeof a PDU session in a process of establishing the PDU session using thecommunications module 703 is as follows. When the IP versioncorresponding to the application is the IP version requested by theapplication, and the first condition includes the IP version requestedby the application, the IP stack capability of the UE, and the IPversion supported by the DNN, the UE sets, in the process ofestablishing the PDU session, the requested PDU type of the PDU sessionto an intersection of the IP version requested by the application, theIP stack capability of the UE, and the IP version supported by the DNN.

For example, the processing module 702 is configured to support the UEin performing the process 202 in FIG. 2, the processes in FIG. 3, theprocess 402 in FIG. 4, the processes in FIG. 5, and the processes 601and 607 in FIG. 6, and/or is configured to perform another process ofthe technology described in this specification. The communicationsmodule 703 is configured to support the UE in communicating with anothernetwork entity, for example, communicating with the PCF. The UE mayfurther include a storage module 701 configured to store program codeand data of the UE.

In this embodiment of the present disclosure, when setting the requestedPDU type of the PDU session in the process of establishing the PDUsession using the communications module 703, the processing module 702considers the IP version corresponding to the application associatedwith the PDU session. Therefore, the requested PDU type of the PDUsession can be consistent with a PDU type requested by the application,such that the application can normally perform communication.

The processing module 702 may be a processor or a controller, such as acentral processing unit (CPU), a general purpose processor, a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a field programmable gate array (FPGA) or another programmablelogic device, a transistor logic device, a hardware component, or acombination thereof. The processing module 702 may implement or executevarious example logical blocks, modules, and circuits described withreference to content disclosed in the present disclosure. Alternatively,the processor may be a combination that implements a computing function,for example, a combination of one or more microprocessors, or acombination of a DSP and a microprocessor. The communications module 703may be a communications interface, a transceiver, a transceiver circuit,or the like. The communications interface is a general term, and mayinclude one or more interfaces. The storage module 701 may be a memory.

When the processing module 702 is a processor, the communications module703 is a communications interface, and the storage module 701 is amemory, the UE in this embodiment of the present disclosure may be a UEshown in FIG. 8.

Referring to FIG. 8, the UE 800 includes a processor 802, acommunications interface 803, and a memory 801. The communicationsinterface 803, the processor 802, and the memory 801 may be connected toeach other using a communication connection.

When an integrated module is used, FIG. 9 is a possible schematicstructural diagram of the PCF in the foregoing embodiment. A PCF 900includes a processing module 902 and a communications module 903. Theprocessing module 902 is configured to control and manage an action ofthe PCF.

In an example, the processing module 902 is configured to send a UEpolicy to a UE using the communications module 903. The UE policyincludes an IP version corresponding to an application, where the IPversion corresponding to the application is used by the UE to set arequested PDU type of a PDU session, and where the application isassociated with the PDU session.

In an example, the IP version corresponding to the application includesan IP version requested by the application or an IP version recommendedby the application.

In an example, before the processing module 902 sends the UE policy tothe UE using the communications module 903, the processing module 902 isfurther configured to determine, based on an IP version supported by aDNN and the IP version requested by the application, the IP versionrecommended by the application. The IP version corresponding to theapplication is the IP version recommended by the application.

In an example, the UE policy further includes the DNN.

For example, the processing module 902 is configured to support the PCFin performing the process 201 in FIG. 2, the process 401 in FIG. 4, andthe process 605 in FIG. 6, and/or is configured to perform anotherprocess of the technology described in this specification. Thecommunications module 903 is configured to support the PCF incommunicating with another network entity, for example, communicatingwith the UE. The PCF may further include a storage module 901 configuredto store program code and data of the PCF.

In this embodiment of the present disclosure, the processing module 902sends the UE policy to the UE using the communications module 903, wherethe UE policy includes the IP version corresponding to the application.As such, the UE can set the requested PDU type of the PDU session basedon the IP version corresponding to the application.

The processing module 902 may be a processor or a controller, such as acentral processing unit (CPU), a general purpose processor, a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a field programmable gate array (FPGA) or another programmablelogic device, a transistor logic device, a hardware component, or acombination thereof. The processing module 902 may implement or executevarious example logical blocks, modules, and circuits described withreference to content disclosed in the present disclosure. Alternatively,the processor may be a combination that implements a computing function,for example, a combination of one or more microprocessors, or acombination of a DSP and a microprocessor. The communications module 903may be a communications interface, a transceiver, a transceiver circuit,or the like. The communications interface is a general term, and mayinclude one or more interfaces. The storage module 801 may be a memory.

When the processing module 902 is a processor, the communications module903 is a communications interface, and the storage module 901 is amemory, the PCF in this embodiment of the present disclosure may be aPCF shown in FIG. 10.

Referring to FIG. 10, the PCF 1000 includes a processor 1002, acommunications interface 1003, and a memory 1001. The communicationsinterface 1003, the processor 1002, and the memory 1001 may be connectedto each other using a communication connection.

All or some of the foregoing embodiments of the present disclosure maybe implemented using software, hardware, firmware, or any combinationthereof. When software is used to implement the embodiments, all or someof the embodiments may be implemented in a form of a computer programproduct. The computer program product includes one or more computerinstructions. When the computer program instructions are loaded andexecuted on the computer, the procedure or functions according to theembodiments of the present disclosure are all or partially generated.The computer may be a general-purpose computer, a dedicated computer, acomputer network, or other programmable apparatuses. The computerinstructions may be stored in a computer readable storage medium or maybe transmitted from a computer readable storage medium to anothercomputer readable storage medium. For example, the computer instructionsmay be transmitted from a web site, computer, server, or data center toanother website, computer, server, or data center in a wired (forexample, a coaxial cable, an optical fiber, or a digital subscriber line(DSL)) or wireless (for example, infrared, radio, or microwave) manner.The computer readable storage medium may be any usable medium accessibleby a computer, or a data storage device, such as a server or a datacenter, integrating one or more usable media. The usable medium may be amagnetic medium (for example, a floppy disk, a hard disk, or a magnetictape), an optical medium (for example, a DVD), a semiconductor medium(for example, a solid state disk (SSD)), or the like.

The objectives, technical solutions, and beneficial effects of thepresent disclosure are further described in detail in the foregoingembodiments. It should be understood that the foregoing descriptions aremerely example embodiments of the present disclosure, and are notintended to limit the protection scope of the present disclosure. Anymodification, equivalent replacement, or improvement made within thespirit and principle of the present disclosure shall fall within theprotection scope of the present disclosure.

1. A protocol data unit (PDU) session establishing method implemented bya terminal device, comprising: receiving a user equipment routeselection policy (URSP) from a policy control function (PCF) entity;determining a PDU session type associated with an application accordingto the URSP; sending a request for establishing a PDU session, whereinthe request comprises the PDU session type; and associating theapplication with the PDU session after the request is accepted.
 2. ThePDU session establishing method according to claim 1, wherein the PDUsession type comprises an Internet Protocol (IP) version associated withthe application.
 3. The PDU session establishing method according toclaim 2, wherein the IP version is supported by the application.
 4. ThePDU session establishing method according to claim 2, wherein the IPversion comprises: IP version 4 (IPv4), IP version 6 (IPv6), or IPv4 andIPv6.
 5. The PDU session establishing method according to claim 1,wherein the URSP comprises a data network name (DNN).
 6. The PDU sessionestablishing method according to claim 1, further comprising sending aregistration request message to an access and mobility managementfunction (AMF) entity, wherein the registration request message carriesa globally unique temporary identity (GUTI) of the terminal device. 7.The PDU session establishing method according to claim 1, wherein theURSP is stored in the PCF entity.
 8. A terminal device, comprising: aprocessor; and a memory coupled to the processor and configured to storea program instruction that, when executed by the processor, causes theterminal device to: receive a user equipment route selection policy(URSP) from a policy control function (PCF) entity; determine a protocoldata unit (PDU) session type associated with an application according tothe URSP; send a request for establishing a PDU session, wherein therequest comprises the PDU session type; and associate the applicationwith the PDU session after the request is accepted.
 9. The terminaldevice according to claim 8, wherein the PDU session type comprises anInternet Protocol (IP) version associated with the application.
 10. Theterminal device according to claim 9, wherein the IP version issupported by the application.
 11. The terminal device according to claim9, wherein the IP version comprises: IP version 4 (IPv4), IP version 6(IPv6), or IPv4 and IPv6.
 12. The terminal device according to claim 8,wherein the URSP comprises a data network name (DNN).
 13. The terminaldevice according to claim 8, wherein when executed by the processor, theprogram instruction further causes the terminal device to send aregistration request message to an access and mobility managementfunction (AMF) entity, and wherein the registration request messagecarries a globally unique temporary identity (GUTI) of the terminaldevice.
 14. The terminal device according to claim 8, wherein the URSPis stored in the PCF entity.
 15. A non-transitory computer readablestorage medium configured to store instructions that, when executed by aprocessor of a user equipment (UE), cause the UE to perform a protocoldata unit (PDU) type setting method comprising: receiving a UE routeselection policy (URSP) from a policy control function (PCF) entity;determining a PDU session type associated with an application accordingto the URSP; sending a request for establishing a PDU session, whereinthe request comprises the PDU session type; and associating theapplication with the PDU session after the request is accepted.
 16. Thenon-transitory computer readable storage medium according to claim 15,wherein the PDU session type comprises an Internet Protocol (IP) versionassociated with the application.
 17. The non-transitory computerreadable storage medium according to claim 16, wherein the IP version issupported by the application.
 18. The non-transitory computer readablestorage medium according to claim 16, wherein the IP version comprises:IP version 4 (IPv4), IP version 6 (IPv6), or IPv4 and IPv6.
 19. Thenon-transitory computer readable storage medium according to claim 15,wherein the URSP comprises a data network name (DNN).
 20. Thenon-transitory computer readable storage medium according to claim 15,wherein when executed by the processor, the instructions further causethe UE to send a registration request message to an access and mobilitymanagement function (AMF) entity, and wherein the registration requestmessage carries a globally unique temporary identity (GUTI) of the UE.